On-board applet migration

ABSTRACT

An electronic device (such as a cellular telephone) automatically installs and personalizes updates to an applet on a secure element in the electronic device. In particular, when a digitally signed update package containing the update is received from an updating device (such as a server), the secure element identifies any previous versions of the applet installed on the secure element. If there are any previously installed versions, the secure element verifies the digital signature of the update package using an encryption key associated with a vendor of the secure element. Then, the secure element uninstalls the previous versions of the applet and exports the associated user data. Next, the secure element installs the update to the applet, and personalizes the new version of the applet using the user data.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/466,850, filed Aug. 22, 2014, now U.S. Pat. No. 9,483,249, issuedNov. 1, 2016, which claims priority to U.S. Provisional PatentApplication No. 61/923,952, filed on Jan. 6, 2014, all of which areherein incorporated by reference in their entireties.

This application is related to U.S. Provisional Patent Application No.62/040,941, filed on Aug. 22, 2014, the content of which is hereinincorporated by reference in its entirety.

BACKGROUND

Field

The described embodiments relate generally to wireless electronicdevices, and more specifically to techniques for updating an appletinstalled on a wireless electronic device.

Related Art

Many modern electronic devices typically include a networking subsystemthat is used to wirelessly communicate with other electronic devices.For example, these electronic devices can include a networking subsystemwith a cellular network interface (UMTS, LTE, etc.), a wireless localarea network interface (e.g., a wireless network such as described inthe Institute of Electrical and Electronics Engineers (IEEE) 802.11standard or Bluetooth™ from the Bluetooth Special Interests Group ofKirkland, Wash.), and/or another type of wireless interface (such as anear-field-communication interface).

Presently, interest is increasing in using such electronic devices toconduct financial transactions. To facilitate this functionality, anelectronic device may include a secure element to provide: security,confidentiality, and one or more application environments. The secureelement may include one or more applets or applications (such as apayment applet associated with a credit card) that execute in anenvironment of the secure element, where the applets allow the secureelement to conduct a financial transaction with another electronicdevice, such as a point-of-sale terminal.

However, it can be difficult to securely update such an applet. Inparticular, if an old version of the applet is uninstalled or deletedprior to installing the new version of the applet, user data may belost. Moreover, migrating the user data from the old version of theapplet to the electronic device prior to the installation poses asecurity risk.

In addition, problems are also associated with installing the newversion of the applet from a secure server. In particular, the servermay become a bottleneck, especially if the applet needs to beconcurrently updated on many electronic devices.

Hence, there is a need for a scalable and secure technique to updateapplets installed on electronic devices.

SUMMARY

The described embodiments relate to an electronic device (such as acellular telephone) that includes: an antenna; an interface circuit thatwirelessly communicates with an updating device (which provides updatesto the electronic device); and a secure element. During operation, thesecure element receives, from the updating device, an update packagewith a digital signature, where the update package includes an update toan applet installed on the secure element. Then, the secure elementidentifies at least one previous version of the applet installed on thesecure element. The secure element may also optionally verify thedigital signature using an encryption key associated with a vendor ofthe secure element. (However, in other embodiments the encryption keymay be associated with a provider of the electronic device and/or acertification authority.) Next, the secure element uninstalls the atleast one previous version of the applet, and exports user dataassociated with the at least one previous version of the applet.Furthermore, the secure element installs the update to the applet, andpersonalizes the applet using the user data.

In some embodiments, prior to installing the update to the applet, thesecure element identifies two or more versions of the applet previouslyinstalled on the secure element, and uninstalls the two or morepreviously installed versions of the applet.

Additionally, prior to installing the update to the applet, the secureelement may decrypt the update package using a second encryption keyassociated with the vendor. This second encryption key may be the sameas or different from the encryption key.

Note that the at least one previous version of the applet may beidentified by searching a registry associated with a normal operatingsystem that is executed by a processor in the secure element.

Moreover, the digital signature may be associated with a privateencryption key of the vendor, and the secure element may verify thedigital signature using a corresponding public encryption key of thevendor. However, in other embodiments symmetric encryption keys areused. Thus, the digital signature may be associated with the encryptionkey of the vendor, and the secure element may optionally verify thedigital signature using the encryption key of the vendor (once again, inother embodiments the encryption key may be associated with a providerof the electronic device and/or a certification authority).

Furthermore, the receiving, identifying, verifying, uninstalling,installing and/or personalizing operations may be performed by anupdating operating system that is executed by the processor in thesecure element, and the updating operating system may be separate fromthe normal operating system, executed by the processor, which performsother functions of the secure element.

In some embodiments, the secure element includes the processor, andmemory, coupled to the processor, which stores a program module executedby the processor. The program module may include instructions for atleast some of the aforementioned operations performed by the secureelement.

Another embodiment provides the secure element.

Another embodiment provides a computer-program product for use inconjunction with the secure element in the electronic device. Thiscomputer-program product may include instructions for at least some ofthe aforementioned operations performed by the secure element.

Another embodiment provides a method for updating the applet installedin the secure element in the electronic device, which may be performedby the processor in the secure element. During operation, the processorreceives, from the updating device, the update package with the digitalsignature, where the update package includes the update to the appletinstalled on the secure element. Then, the processor identifies the atleast one previous version of the applet installed on the secureelement. The processor also verifies the digital signature using theencryption key associated with the vendor of the secure element. Next,the processor uninstalls the at least one previous version of the appletand exports the user data associated with the at least one previousversion of the applet. Furthermore, the processor installs the update tothe applet, and personalizes the applet using the user data.

Another embodiment provides a system that includes the electronic deviceand the updating device.

The preceding summary is provided for purposes of summarizing someexemplary embodiments to provide a basic understanding of aspects of thesubject matter described herein. Accordingly, the above-describedfeatures are merely examples and should not be construed as narrowingthe scope or spirit of the subject matter described herein in any way.Other features, aspects, and advantages of the subject matter describedherein will become apparent from the following Detailed Description,Figures, and Claims.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram illustrating electronic devices communicatingin accordance with an embodiment of the present disclosure.

FIG. 2 is a block diagram illustrating one of the electronic devices ofFIG. 1 in accordance with an embodiment of the present disclosure.

FIG. 3 is a flow diagram illustrating a method for updating an appletinstalled on one of the electronic devices in FIG. 1 in accordance withan embodiment of the present disclosure.

FIG. 4 is a flow diagram illustrating a method for uninstalling aversion of an applet and exporting personal data in one of theelectronic devices in FIG. 1 in accordance with an embodiment of thepresent disclosure.

FIG. 5 is a drawing illustrating communication within one of theelectronic devices in FIG. 1 in accordance with an embodiment of thepresent disclosure.

FIG. 6 is a flow diagram illustrating a method for installing a newversion of an applet and importing personal data in one of theelectronic devices in FIG. 1 in accordance with an embodiment of thepresent disclosure.

FIG. 7 is a drawing illustrating communication within one of theelectronic devices in FIG. 1 in accordance with an embodiment of thepresent disclosure.

FIG. 8 is a drawing illustrating registry entries in a secure element inone of the electronic devices in FIG. 1 in accordance with an embodimentof the present disclosure.

FIG. 9 is a drawing illustrating a preflight script in the method ofFIG. 6 in accordance with an embodiment of the present disclosure.

Note that like reference numerals refer to corresponding partsthroughout the drawings. Moreover, multiple instances of the same partare designated by a common prefix separated from an instance number by adash.

DETAILED DESCRIPTION

An electronic device (such as a cellular telephone) automaticallyinstalls and personalizes updates to an applet on a secure element inthe electronic device (which is sometimes referred to as ‘appletmigration’). In particular, when a digitally signed update packagecontaining the update is received from an updating device (such as aserver), the secure element identifies any previous versions of theapplet installed on the secure element. If there are any previouslyinstalled versions, the secure element may optionally verify the digitalsignature of the update package using an encryption key associated witha vendor of the secure element. (However, in other embodiments theencryption key is associated with a provider of the electronic deviceand/or a certification authority.) Then, the secure element uninstallsthe previous versions of the applet and exports the associated userdata. Next, the secure element installs the update to the applet, andpersonalizes the new version of the applet using the user data. In thisway, the electronic device provides a scalable update solution whilemaintaining the personalization from the previous versions of theapplet.

The update package may be received via wireless communication betweenthe electronic device and the updating device. This wirelesscommunication may involve conveying packets that are transmitted andreceived by radios in the electronic device and the updating device inaccordance with a communication protocol, such as an Institute ofElectrical and Electronics Engineers (IEEE) 802.11 standard, Bluetooth™(from the Bluetooth Special Interests Group of Kirkland, Wash.), and/oranother type of wireless interface, such as a near-field-communicationstandard or specification (from the NFC Forum of Wakefield, Mass.). Inaddition, the communication protocol may be compatible with a 3^(rd)generation of mobile telecommunications technology (such as acommunication protocol that complies with the International MobileTelecommunications-2000 specifications by the InternationalTelecommunication Union of Geneva, Switzerland), a 4^(th) generation ofmobile telecommunications technology (such as a communication protocolthat complies with the International Mobile Telecommunications Advancedspecification by the International Telecommunication Union of Geneva,Switzerland), and/or another cellular-telephone communication technique.In the discussion that follows, a cellular-telephone communicationtechnique is used as an illustrative example.

The communication between the electronic device and the updating deviceis shown in FIG. 1, which presents a block diagram illustratingelectronic device 110 and updating device 112 communicating. Asdescribed further below with reference to FIGS. 3-7, these electronicdevices may communicate when updating device 112 (such as a server or anupdate computer) provides an update package with an update to a previousversion of an applet (i.e., a new version of the applet) that isinstalled on electronic device 110 (such as a cellular telephone). Forexample, the previous version of the applet may be installed on a secureelement in electronic device 110. In addition, a user of electronicdevice 110 may have previously customized or personalized the previousversion with user data.

In the update technique described below, the secure element determinesif the update package is relevant for electronic device 110 byidentifying at least one (and, in some embodiments, all) previouslyinstalled versions (or alternatively, instances) of the applet. Then,the secure element authenticates the update package by verifying adigital signature, which is associated with a vendor of the secureelement. (Alternatively, the digital signature may be associated with aprovider of electronic device 110 or an applet installed on a secureelement in electronic device 110.) For example, the secure element mayuse an encryption key associated with the vendor (such as a publicencryption key) to verify the update package. In addition, the secureelement may decrypt the update package using a second encryption key,which may be the same or different from the encryption key. In anexemplary embodiment, a public-private encryption-key technique is used.In particular, the update package may be signed using the privateencryption key of the vendor, and the digital signature may be verifiedand the update package may be decrypted using the public encryption keyof the vendor. However, in other embodiments a symmetric encryptiontechnique is used. Thus, the same encryption key may be used to sign,encrypt and/or decrypt the update package.

Then, the secure element uninstalls the at least one (and, in someembodiments, all) previous versions of the applet and exports theassociated user data. Next, the secure element installs the update tothe applet, and personalizes the new version of the applet using theuser data.

In these ways, electronic device 110 and updating device 112 may be usedto securely and flexibly disseminate and install personalized updates toone or more applets previously installed on electronic device 110, whilemigrating or keeping the associated user data.

As noted previously, the communication between electronic device 110and/or updating device 112 may involve the exchange of packets thatinclude the update package. These packets may be included in frames inone or more wireless channels.

As described further below with reference to FIG. 2, electronic device110 and/or updating device 112 may include subsystems, such as: anetworking subsystem, a memory subsystem, a processing subsystem and asecure subsystem. In addition, electronic device 110 and/or updatingdevice 112 may include radios 114 in the networking subsystems. Moregenerally, electronic device 110 and/or updating device 112 can include(or can be included within) any electronic devices with networkingsubsystems that enable electronic device 110 and/or updating device 112to wirelessly communicate with another electronic device. This cancomprise transmitting frames on wireless channels to enable electronicdevices to make initial contact, followed by exchanging subsequentdata/management frames (such as connect requests to establish aconnection), configuring security options (e.g., IPSEC), transmittingand receiving packets or frames, etc.

As can be seen in FIG. 1, wireless signals 116 (represented by a jaggedline) are transmitted from/received by a radio 114-1 in electronicdevice 110. These wireless signals are received by/transmitted fromradio 114-2 in updating device 112. (Note that the communication betweenelectronic device 110 and/or updating device 112 may also occur vianetwork 118, which may involve wired communication with a differentcommunication protocol than wireless signals 116.) Moreover, thewireless communication may or may not involve a connection beingestablished between electronic device 110 and/or updating device 112,and therefore may or may not involve communication via a wirelessnetwork (such as a cellular-telephone network).

In the described embodiments, processing a packet or frame in electronicdevice 110 and/or updating device 112 includes: receiving wirelesssignals 116 with the packet or frame; decoding/extracting the packet orframe from received wireless signals 116 to acquire the packet or frame;and processing the packet or frame to determine information contained inthe packet or frame (such as at least a portion of the update package).

As noted previously, in general communication between electronic device110 and/or updating device 112 may be encrypted. This encryption may usean encryption key (such as an encryption key associated with the appletand/or the vendor of the secure element). Furthermore, the encryptionmay use symmetric or asymmetric encryption techniques.

Although we describe the environment shown in FIG. 1 as an example, inalternative embodiments, different numbers or types of electronicdevices may be present. For example, some embodiments comprise more orfewer electronic devices. As another example, in another embodiment,different electronic devices transmit and/or receive packets or frames.

We now describe embodiments of the electronic device. FIG. 2 presents ablock diagram illustrating electronic device 110. This electronic deviceincludes processing subsystem 210, memory subsystem 212, networkingsubsystem 214, authentication subsystem 216 and secure subsystem 218.Processing subsystem 210 includes one or more devices configured toperform computational operations. For example, processing subsystem 210can include one or more microprocessors, application-specific integratedcircuits (ASICs), microcontrollers, programmable-logic devices, and/orone or more digital signal processors (DSPs).

In addition, processing subsystem 210 may include a secure enclaveprocessor 220 (which is a system-on-chip within one or more processorsin processing subsystem 210) that performs security services for othercomponents in the processing subsystem 210 and that securelycommunicates with other subsystems in electronic device 110. Secureenclave processor 220 may include one or more processors, a secure bootROM, one or more security peripherals, and/or other components. Thesecurity peripherals may be hardware-configured to assist in the secureservices performed by secure enclave processor 220. For example, thesecurity peripherals may include: authentication hardware implementingvarious authentication techniques, encryption hardware configured toperform encryption, secure-interface controllers configured tocommunicate over the secure interface to other components, and/or othercomponents. In some embodiments, instructions executable by secureenclave processor 220 are stored in a trust zone in memory subsystem 212that is assigned to secure enclave processor 220, and secure enclaveprocessor 220 fetches the instructions from the trust zone forexecution. Secure enclave processor 220 may be isolated from the rest ofprocessing subsystem 210 except for a carefully controlled interface,thus forming a secure enclave for secure enclave processor 220 and itscomponents. Because the interface to secure enclave processor 220 iscarefully controlled, direct access to components within secure enclaveprocessor 220 (such as a processor or a secure boot ROM) may beprevented. In some embodiments, secure enclave processor 220 encryptsand/or decrypts authentication information communicated withauthentication subsystem 216, and encrypts and/or decrypts information(such as tokens) communicated with secure subsystem 218. Furthermore,secure enclave processor 220 may compare authentication information withstored authentication and, if a match is obtained, may provide anencrypted token with an authentication-complete indicator to a secureelement 230 and/or may assert the authentication-complete indicator as aflag in operating system 244.

Memory subsystem 212 includes one or more devices for storing dataand/or instructions for processing subsystem 210, networking subsystem214, authentication subsystem 216 and/or secure subsystem 218. Forexample, memory subsystem 212 can include dynamic random access memory(DRAM), static random access memory (SRAM), and/or other types ofmemory. In some embodiments, instructions for processing subsystem 210in memory subsystem 212 include: one or more program modules or sets ofinstructions (such as program module 246, e.g., a digital wallet, apassbook and/or a mobile payments application), which may be executed byprocessing subsystem 210. Note that the one or more computer programsmay constitute a computer-program mechanism or a program module.Moreover, instructions in the various modules in memory subsystem 212may be implemented in: a high-level procedural language, anobject-oriented programming language, and/or in an assembly or machinelanguage. Furthermore, the programming language may be compiled orinterpreted, e.g., configurable or configured (which may be usedinterchangeably in this discussion), to be executed by processingsubsystem 210.

In addition, memory subsystem 212 can include mechanisms for controllingaccess to the memory. In some embodiments, memory subsystem 212 includesa memory hierarchy that comprises one or more caches coupled to a memoryin electronic device 110. In some of these embodiments, one or more ofthe caches is located in processing subsystem 210.

In some embodiments, memory subsystem 212 is coupled to one or morehigh-capacity mass-storage devices (not shown). For example, memorysubsystem 212 can be coupled to a magnetic or optical drive, asolid-state drive, or another type of mass-storage device. In theseembodiments, memory subsystem 212 can be used by electronic device 110as fast-access storage for often-used data, while the mass-storagedevice is used to store less frequently used data.

Networking subsystem 214 includes one or more devices configured tocouple to and communicate on a wired and/or wireless network (i.e., toperform network operations), including an interface circuit 222 (such asa near-field-communication circuit) and an antenna 224. For example,networking subsystem 214 can include a Bluetooth™ networking system, acellular networking system (e.g., a 3G/4G network such as UMTS, LTE,etc.), a universal serial bus (USB) networking system, a networkingsystem based on the standards described in IEEE 802.11 (e.g., a Wi-Fi®networking system), an Ethernet networking system, and/or anothercommunication system (such as a near-field-communication system).

Networking subsystem 214 includes processors, controllers,radios/antennas, sockets/plugs, and/or other devices used for couplingto, communicating on, and handling data and events for each supportednetworking or communication system. Note that mechanisms used forcoupling to, communicating on, and handling data and events on thenetwork for each network system are sometimes collectively referred toas a ‘network interface’ for the network system. Moreover, in someembodiments a ‘network’ between the electronic devices does not yetexist. Therefore, electronic device 110 may use the mechanisms innetworking subsystem 214 for performing simple wireless communicationbetween electronic device 110 and updating device 112 (FIG. 1), e.g.,transmitting advertising frames and/or near-field communication.

Authentication subsystem 216 may include one or more processors,controllers and devices for receiving the authentication informationfrom a user of electronic device 110, and for securely communicatingthis authentication information to processing subsystem 210 (such as byencrypting the authentication information). For example, theauthentication information may include: a biometric identifier acquiredby a biometric sensor 226 (such as: a fingerprint sensor, a retinalsensor, a palm sensor, a digital signature-identification sensor, etc.);a personal identification number (PIN) associated with one of paymentapplets 236 that is received using a user-interface device 228 (such asa keypad, a touch-sensitive display, optical character recognitionand/or voice recognition); and a passcode for unlocking at least somefunctionality of electronic device 110 that is received usinguser-interface device 228.

Furthermore, secure subsystem 218 may include a secure element 230,which includes one or more processors and memory. Note that secureelement 230 may be a tamper-resistant component that is used inelectronic device 110 to provide the security, confidentiality, andmultiple application environments required to support various businessmodels. Secure element 230 may exist in one or more of a variety of formfactors, such as: a universal integrated circuit card (UICC), anembedded secure element (on a circuit board in electronic device 110), asmart secure digital (SD) card, a smart microSD card, etc.

Moreover, secure element 230 may include one or more applets orapplications that execute in an environment of secure element 230 (suchas in operating system 232 of secure element 230, and/or in a Javaruntime environment executing on the secure element 230). For example,the one or more applets may include an authentication applet that:performs contactless registry services, encrypts/decrypts packets ortokens communicated with secure enclave processor 220, sets one or moresoftware flags (such as an authentication-complete flag) in operatingsystem 232 of secure element 230, and/or conveys information to one ormore payment applets 236. The one or more applets may include one ormore payment applets 236 that conduct financial transactions withanother electronic device when they are activated by program module 246,and based on the one or more software flags and/or when electronicdevice 110 is proximate to the other electronic device. In particular,payment applets 236 may each be associated with a financial vehicle(such as a credit card, a debit card, a prepaid debit card, a gift cardand, more generally, a financial vehicle provided by a financialinstitution, e.g., a bank, that is associated with a financial accountof a user, such as a user of electronic device 110). In addition, secureelement 230 may include information associated with the one or morepayment applets 236 (such as a financial credential, e.g., a deviceprimary account number or DPAN, a PIN, e.g., a debit-card number, whichis associated with a given payment applet, and one or more encryptionkeys that are associated with the given payment applet) that is usedwhen conducting the financial transactions. (Note that the DPAN may beassociated with, but different than, a financial primary account numberor FPAN for the financial account, such as a credit-card number. TheDPAN may be a virtual identifier for the financial account.)

The authentication applet may execute in a master or issuer securitydomain in secure element 230 (such as controlling authority securitydomain), while payment applets 236 may execute in supplemental securitydomains. Communication between these security domains may be encryptedusing different encryption/decryption keys that are security-domainspecific. In electronic device 110 and/or during communication betweenelectronic device 110 and/or updating device 112 (FIG. 1),encryption/decryption may involve symmetric and/or asymmetricencryption. In addition, the information communicated may also include adigital signature that is specific to electronic device 110 and/orcomponents in electronic device 110, such as secure element 230 or oneof payment applets 236.

During operation of electronic device 110, the user may use passbook 248to select or activate one or more of payment applets 236. If the paymentapplet supports an authentication-complete flag (as indicated by theenabling or setting of authentication support in the payment applet), inorder for the payment applet to conduct a financial transaction withanother electronic device, the payment applet may need to be activatedand the authentication-complete flag may need to be set or enabled insecure element 230 (indicating that the user has been authenticated). Incontrast, for one of payment applets 236 that does not support theauthentication-complete flag, a financial transaction may be conductedwhen this payment applet is active (i.e., operation of the paymentapplet is not gated by the setting or enabling of theauthentication-complete flag in secure element 230). While the presentdiscussion illustrates the use of a global authentication-complete flag,note that in some embodiments separate authentication-complete flags areassociated with at least some of payment applets 236 (i.e., there may bea specific authentication-complete flag for a given payment applet,etc.).

When electronic device 110 is proximate to the other electronic device(such as a point-of-sale terminal) or when secure enclave processor 220provides a payment command to secure element 230, one of the specified,activated and/or authenticated payment applets 236 may provide a paymentpacket (which may be encrypted or unencrypted) to interface circuit 222or to secure enclave processor 220 (which then provides the paymentpacket to interface circuit 222). Then, interface circuit 222 maycommunicate the payment packet to the other electronic device (such as apoint-of-sale terminal) using antenna 224. Note that the payment packetmay include financial information (such as a financial credential or aDPAN associated with the one of the payment applets 236).

This financial information (as well as additional information providedby the other electronic device, such as a merchant identifier, an amountof the financial transaction, etc.) may be communicated by the otherelectronic device to a payment network 118 (FIG. 1) to complete afinancial transaction. Once the financial transaction is complete, anotification from a management electronic device (which may beassociated with a provider of electronic device 110) may be received byinterface circuit 222. Passbook 248 may provide the notification todisplay subsystem 240 for display, so the user of electronic device 110can be alerted that the financial transaction was successfullycompleted.

As noted previously, during the update technique electronic device 110may receive the digitally signed update package from updating device 112(FIG. 1). In particular, interface circuit 222 may receive the updatepackage, and may provide the update package to secure enclave processor220. Then, secure enclave processor 220 may securely communicate theupdate package to secure element 230. In response, operating system 232(or a program module executed by a processor in secure element 230 in anenvironment of operating system 232) may identify at least one previousversion of one of applets 236 (such as a payment applet), which isinstalled on secure element 230. For example, the at least one previousversion of one of applets 236 may be identified by searching a registryassociated with operating system 232.

Moreover, operating system 232 may optionally verify the digitalsignature using an encryption key associated with a vendor of secureelement 230 (or a vendor of the applet). However, in other embodimentsthe encryption key is associated with a provider of the electronicdevice and/or a certification authority.

In some embodiments, operating system 232 decrypts the update packageusing a second encryption key associated with the vendor of secureelement 230 (or the vendor of the applet). This second encryption keymay be the same as or different from the encryption key.

Next, operating system 232 may uninstall the at least one previousversion of the applet, and may export user data associated with the atleast one previous version of the applet. Furthermore, operating system232 may install the update to the applet, and may personalize the appletusing the user data. The uninstalling (or deleting), exporting,installing and personalizing of the applet may occur within a securitydomain on secure element 230.

Note that one or more of the aforementioned operations performed byoperating system 232 may be performed by an updating operating system234 (such as a high-end boot loader) that is executed by the processorin the secure element. This updating operating system may be separatefrom operating system 232, which performs other functions of secureelement 230. Updating operating system 234 may update portions ofoperating system 232 and/or software associated with one or more ofapplets 236.

Within electronic device 110, processing subsystem 210, memory subsystem212, networking subsystem 214, authentication subsystem 216 and securesubsystem 218 may be coupled using one or more interconnects, such asbus 238. These interconnects may include an electrical, optical, and/orelectro-optical connection that the subsystems can use to communicatecommands and data among one another. Note that different embodiments caninclude a different number or configuration of electrical, optical,and/or electro-optical connections among the subsystems. In someembodiments, electronic device 110 can detect tampering with securecomponents (such as secure enclave processor 220, secure element 230and/or bus 238) and may destroy encryption/decryption keys orauthentication information (such as a stored biometric identifier) iftampering is detected.

In some embodiments, electronic device 110 includes display subsystem240 for displaying information on a display (such as a notification of asuccessfully completed financial transaction), which may include adisplay driver and the display, such as a liquid-crystal display, amulti-touch touchscreen, etc. In addition, in some embodimentselectronic device 110 includes a secure input/output (I/O) subsystem 242(such as a keypad) for receiving the PIN of the user that is associatedwith one of payment applets 236. As noted previously, display subsystem240 and/or secure I/O subsystem 242 may be included in authenticationsubsystem 216.

Electronic device 110 can be (or can be included in) any electronicdevice with at least one network interface. For example, electronicdevice 110 can be (or can be included in): a desktop computer, a laptopcomputer, a server, a media player (such as an MP3 player), anappliance, a subnotebook/netbook, a tablet computer, a smartphone, acellular telephone, a piece of testing equipment, a network appliance, aset-top box, a personal digital assistant (FDA), a toy, a controller, adigital signal processor, a game console, a computational engine withinan appliance, a consumer-electronic device, a portable computing device,a personal organizer, and/or another electronic device.

Although specific components are used to describe electronic device 110,in alternative embodiments, different components and/or subsystems maybe present in electronic device 110. For example, electronic device 110may include one or more additional processing subsystems, memorysubsystems, networking subsystems, authentication subsystems, securesubsystems, display subsystems and/or secure I/O subsystems.Additionally, one or more of the subsystems may not be present inelectronic device 110. Moreover, in some embodiments, electronic device110 may include one or more additional subsystems that are not shown inFIG. 2. For example, electronic device 110 can include, but is notlimited to, a data collection subsystem, an audio and/or videosubsystem, an alarm subsystem, and/or a media processing subsystem.Also, although separate subsystems are shown in FIG. 2, in someembodiments, some or all of a given subsystem or component can beintegrated into one or more of the other subsystems or components inelectronic device 110. For example, in some embodiments program module246 is included in operating system 244. Alternatively or additionally,at least some of the functionality of program module 246 may be includedin passbook 248.

Moreover, the circuits and components in electronic device 110 may beimplemented using any combination of analog and/or digital circuitry,including: bipolar, PMOS and/or NMOS gates or transistors. Furthermore,signals in these embodiments may include digital signals that haveapproximately discrete values and/or analog signals that have continuousvalues. Additionally, components and circuits may be single-ended ordifferential, and power supplies may be unipolar or bipolar.

An integrated circuit may implement some or all of the functionality ofnetworking subsystem 214 (such as a radio) and, more generally, some orall of the functionality of electronic device 110. Moreover, theintegrated circuit may include hardware and/or software mechanisms thatare used for transmitting wireless signals from electronic device 110to, and receiving signals at electronic device 110 from updating device112 (FIG. 1). Aside from the mechanisms herein described, radios aregenerally known in the art and hence are not described in detail. Ingeneral, networking subsystem 214 and/or the integrated circuit caninclude any number of radios. Note that the radios in multiple-radioembodiments function in a similar way to the radios described insingle-radio embodiments.

In some embodiments, networking subsystem 214 and/or the integratedcircuit include a configuration mechanism (such as one or more hardwareand/or software mechanisms) that configures the radio(s) to transmitand/or receive on a given communication channel (e.g., a given carrierfrequency). For example, in some embodiments, the configurationmechanism can be used to switch the radio from monitoring and/ortransmitting on a given communication channel to monitoring and/ortransmitting on a different communication channel. (Note that‘monitoring’ as used herein comprises receiving signals from otherelectronic devices and possibly performing one or more processingoperations on the received signals, e.g., determining if the receivedsignal comprises an advertising frame, etc.)

While a communication protocol compatible with a cellular-telephonenetwork was used as an illustrative example, the described embodimentsof the update technique may be used in a variety of network orcommunication interfaces. Furthermore, while some of the operations inthe preceding embodiments were implemented in hardware or software, ingeneral the operations in the preceding embodiments can be implementedin a wide variety of configurations and architectures. Therefore, someor all of the operations in the preceding embodiments may be performedin hardware, in software or both.

While the preceding discussion focused on the hardware, software andfunctionality in electronic device 110, updating device 112 (FIG. 1) mayhave the same or similar hardware (processors, memory, networkinginterfaces, etc.) and/or software to support the operations performed bythese entities, as described further below with reference to FIGS. 3-7.In particular, these entities may include one or more computer systemswith a processing subsystem that executes one or more program modulesstored in a memory subsystem to perform the operations, and one or morenetworking interfaces for communicating with other electronic devices,such as electronic device 110.

We now further describe updating or migrating the applet installed onthe secure element in the electronic device. FIG. 3 presents a flowdiagram illustrating a method 300 for updating an applet installed onpan electronic device (such as electronic device 110 in FIG. 1), whichmay be performed by a processor in a secure element in the electronicdevice. For example, the processor may execute a program module thatincludes instructions for operations in method 300. During operation,the processor receives, from an updating device, an update package witha digital signature (operation 310), where the update package includesan update to the applet installed on the secure element.

Then, the processor identifies at least one previous version of theapplet (operation 312) installed on the secure element. For example, thesecure element may identify two or more versions of the appletpreviously installed on the secure element, and may uninstall the two ormore previously installed versions of the applet. In some embodiments,the secure element identifies all the previously installed versions ofthe applet, and uninstalls all of the previously installed versions ofthe applet. Note that the at least one previous version of the appletmay be identified by searching a registry associated with a normaloperating system that is executed by a processor in the secure element.

Moreover, the processor optionally verifies the digital signature usingan encryption key (operation 314), which may be associated with a vendorof the secure element. (However, in other embodiments the encryption keyis associated with a provider of the electronic device and/or acertification authority.) In particular, the digital signature may beassociated with a private encryption key of the vendor, and the secureelement may verify the digital signature using a public encryption keyof the vendor. However, in other embodiments symmetric encryption keysare used. Thus, in these embodiments the digital signature may beassociated with the encryption key of the vendor, and the secure elementmay verify the digital signature using the encryption key of the vendor.

In some embodiments, the secure element optionally decrypts the updatepackage (operation 316) using a second encryption key, which may beassociated with the vendor. This second encryption key may be the sameas or different from the encryption key.

Next, the processor uninstalls the at least one previous version of theapplet, and exports user data (operation 318) associated with the atleast one previous version of the applet.

Furthermore, the processor installs the update to the applet, andpersonalizes the applet using the user data (operation 320).

Note that one or more of the operations in method 300 may be performedby an updating operating system that is executed by the processor in thesecure element, and the updating operating system may be separate fromthe normal operating system, executed by the processor, which performsother functions of the secure element. (Alternatively, one or more ofthe operations in method 300 may be performed by the normal operatingsystem or by a program module executing in an environment associatedwith the normal operating system.) This approach is illustrated furtherbelow with reference to FIGS. 4 and 6.

In an exemplary embodiment, the update technique allows updates to oneor more Java Card applets on an electronic device that includes a secureelement (such as secure element 230 in FIG. 2). In addition toinstantiating or installing the new version (or, alternatively, the newinstance) of the applet, the update technique may securely transfer ofuser data from the previous version(s) of the applet (e.g., thecurrently installed version) to the new version of the applet, and mayuninstall (or delete) the previous version(s) of the applet. This updatetechnique may address several problems and challenges associated withsecure updates to Java Card applets installed on a secure element.

In particular, in existing update techniques a Java Card applet may beloaded onto the secure element in the form a binary (executable loadfile). An applet instance or version may be installed from thesebinaries and may be used to support a variety of use-cases. Note that anupdate package may include binaries for one or more applets having acommon class application identifier, or class AID (thus, updates forapplets having different class AIDs may be included in different updatepackages). Updates to the applet software typically involve loading thebinary for a new version to the secure element, installing the newversion of the applet and then personalizing the new version of theapplet.

However, once the new binary is loaded onto the secure element, theremay not be any information that the secure element can use to determinethat the new binary is a new version of an existing binary and toproceed with the creation of new versions of the applets for each of theversions of the installed applets associated with the new binary.Consequently, in the existing update technique a new instance may needto be created for each instance or version currently installed on thesecure element.

Furthermore, the applets may use user data that can be populated duringa personalization phase and/or during its use. However, in the absenceof an approach for securely transferring this data from one appletinstance to another in the existing update techniques, a time-consumingre-personalization operation may be needed and/or the user data may belost.

In addition, by requiring two versions of the same binary to bemaintained along with twice the number of applet instances, the existingupdate techniques may constrain limited memory in the secure element.

In the disclosed update technique, a supplemental-security-domaindata-store global service in the secure element (such as secure element230 in FIG. 2) provides encryption key management and communicationaccess to external entities (such as updating device 112 in FIG. 1).Moreover, security domains on the secure element may expose a globalservice to their associated applications, allowing them to import andexport data to a secure data store managed by the supplemental securitydomain.

As described below with reference to FIGS. 4 and 5, when the electronicdevice receives an update package (which may include newoperating-system code, a new package or binary with a different AID thanthe current package AID, and/or metadata), an on-board (or internal)deletion and data-export process may occur. Then, as described belowwith reference to FIGS. 6 and 7, an on-board installation andapplet-personalization process may occur.

Moreover, during these processes one or more registry-entry objects inthe normal operating system (such as operating system 232 in FIG. 2) maybe augmented with a ‘secondary AID’ field. In particular, a registryentry for an instance or version of an applet may include: a packageAID, a class AID, an AID, a secondary AID, an associated securitydomain, privileges, and a life-cycle state. The metadata section in theupdate package may include the package AID, as well as the package AIDsof the previous versions of the applet signed using the operating-systemupdate private-verification encryption key.

After receiving the update package, the secure enclave processor (suchas secure enclave processor 220 in FIG. 2) may extract the metadata anduse it to construct an update-applets command (which is sometimesreferred to as an ‘update-applets application-protocol-data-unitcommand’) that it sends to the secure element. Then, the secure elementmay receive the update-applets command sent to the master or issuersecurity domain.

As shown in FIG. 4, which presents a flow diagram illustrating a method400 for uninstalling a version of an applet and exporting personal datain electronic device 110 (FIG. 1), in response to receiving theupdate-applets command the normal operating system in the secure elementmay browse the registry searching for the current package AID (CPAID).If a similar package AID is found, the normal operating system mayproceed with the verification of the digital signature of the metadata.Moreover, if the signature verification is successful, the secureelement may start the on-board deletion. The normal operating system maythen raise an ‘on_board_flag’ in the registry entry of the package. Thison_board_flag may be kept raised until the installation andpersonalization process described below is complete. In addition, thenormal operating system may copy the current package AID into thesecondary AID field of the package registry entry. Thus, the registryentry for a package may include the on_board_load flag and one moreapplet entries. Each of these applet entries for the package may includean associated on_board_install flag, as well as the package AID, theclass AID, the AID, the secondary AID, the associated security domain,the privileges, and the life-cycle state.

Furthermore, the normal operating system may browse the registry for allapplets instantiated from the package to be updated. For each applet (1to N), the normal operating system may raise the following flags in theregistry entry for the current version of the applet (CVA):‘on_board_install’ (which may be kept raised until the correspondingapplet from the update package has been installed) and ‘on_board_perso’(which may be kept raised until the corresponding applet from the updatepackage has been personalized using the migrated user data).

Additionally, the normal operating system may store the new version ofthe applet (NVA) AID provided in the update table in the update packagein each corresponding registry entry. This AID may replace the currentversion of the applet AID once the on_board_install flag has beenlowered. Note that for applet AIDs which are not included in the updatetable, the current version of the applet AID may be populated in thesecondary AID field.

Moreover, note that each version or instance to be deleted (includingthe applets not present in the update table) may be triggered prior toits deletion and may export its user data to its associated supplementalsecurity domain (SSD). As described previously, the supplementalsecurity domain may implement a global service and expose the data-storeinterface. Upon receipt of a global-service request, the associatedsupplemental security domain may check that the applet requesting theglobal service is one of its associated applications based on theregistry entry of the applet.

Once all current versions of the applets have been successfully deleted,the normal operating system in the secure element may block anysubsequent application-protocol-data-unit messages (i.e., atomicmessages between entities or components in the electronic device)except: a command selecting the issuer security domain; and anotherupdate-applets command. Thus, the normal operating system may rejectother application-protocol-data-unit commands (e.g., with a particularstatus word).

The communication within electronic device 110 during method 400 isshown in FIG. 5. In particular, secure enclave processor 220 (and, moregenerally, processing subsystem 210 in FIG. 2) may provide metadata froman update packet to issuer security domain (ISD) 510 in secure element230. This is forwarded as an export command to a current version of theapplet (CVA) 512, which requests the supplemental security domain forglobal service from operating system 232. After receiving informationspecifying supplemental security domain (SSD) 514, CVA 512 requests theregistry-entry object or pointer from operating system 232.

Then, CVA 512 confirms it is associated with SSD 514, which in turnconfirms the association with operating system 232. Next, SSD 514provides a handle to the data store to CVA 512. In response, CVA 512exports user data to SSD 514, and indicates that it is done to ISD 510,which in turn notifies secure enclave processor 220.

After the current versions of the applet instances or versions have beensuccessfully deleted and their user data has been successfully exportedto their associated security domain, the electronic device (such as thesecure enclave processor) may trigger the secure element to boot inoperating-system update mode (i.e., updating operating system 234 inFIG. 2 may be used). Then, the electronic device may send theoperating-system update bundle to the secure element, which optionallyupdates its operating-system software in addition to storing the updatepackages in its memory. In addition, the updating operating system maypopulate the package AID field with the new package AID value. Note thatthe updating operating system and the normal operating system mayexchange information via flags, such as the on_board_load flag.

After the operating-system update, the electronic device may send anupdate-applets application-protocol-data-unit command to the issuersecurity domain. Then, as shown in FIG. 6, which presents a flow diagramillustrating a method 600 for installing a new version of an applet andimporting personal data on electronic device 110 (FIG. 1), the normaloperating system (such as operating system 232 in FIG. 2) may browse theregistry for the package with on_board_load flag raised. If an update ornew package has been uploaded, the update package AID may be present inthe secondary AID field of the registry entry for the package.Otherwise, the current package AID may be present.

If an update package has been uploaded, the normal operating system maycreate a new instance or version for each applet (1 to N) having aregistry entry flagged with the on_board_(—) install flag. Inparticular, the normal operating system may first replace the currentpackage AID field of the registry entry for the applet with the updateor new package AID, and then may replace the AID field of the registryentry for the applet with the update or new version of the applet AIDpreviously stored in the secondary AID field of the registry entry forthe applet.

Alternatively, if no update or new package has been uploaded, the normaloperating system may re-create all the instances or versions deletedduring the on-board delete.

If the installation is successful, the normal operating system may lowerthe on_board_install flag and the normal operating system may clear thesecondary AID field of the registry entry for the applet. Note that eachupdate or new version of the applet may be triggered during itsinstallation and may import its data from its associated securitydomain.

Moreover, if the user data has been successfully imported (i.e., theinstalled new version of the applet has been personalized), the normaloperating system may lower the on_board_perso flag in the registry entryfor the applet.

The installation of the update or new versions of the applets may takeplace within the context of the update-appletsapplication-protocol-data-unit command. If an error is reported by thesecure element, the electronic device may send another update-appletsapplication-protocol-data-unit command.

Note that the normal operating system in the secure element may enforcea rule that only one successful update-appletsapplication-protocol-data-unit command can be processed after theoperating-system update takes place. However, the electronic device cansend multiple update-applets application-protocol-data-unit commandsuntil it receives a completion response from the issuer security domain.

After all applet instances or versions have been created andre-personalized, the normal operating system in the secure element maylower the on_board_load flag from the registry entry for the package andmay clear the secondary AID field.

The communication within electronic device 110 during method 600 isshown in FIG. 7. In particular, secure enclave processor 220 (and, moregenerally, processing subsystem 210 in FIG. 2) may provide an updatecommand to issuer security domain (ISD) 510 in secure element 230. Thisis forwarded as an import command to an update or new version of theapplet (NVA), which requests the supplemental security domain for globalservice from operating system 232. After receiving informationspecifying (SSD) 514, NVA 710 requests the registry-entry object orpointer from operating system 232.

Then, NVA 710 confirms that it is associated with SSD 514, which in turnconfirms the association with operating system 232. Next, SSD 514provides a handle to the data store to NVA 710. In response, NVA 710imports user data from SSD 514, and indicates that it is done to ISD510, which in turn notifies secure enclave processor 220.

As noted previously, the registry entries for a package may be updatedduring the update technique. This is illustrated in FIG. 8, whichpresents registry entries for a credit-card package with a package AIDand three associated instances of credit-card payment applets before andafter an update.

In these ways, the update technique may facilitate secure and scalabledissemination, installation and personalization of updates to one ormore applets previously installed on electronic devices.

Note that the operations illustrated in FIGS. 5 and 7 may includechallenge and response operations, which are not shown for clarity.

In some embodiments of methods 300 (FIG. 3), 400 (FIG. 4) and 600 (FIG.6), there may be additional or fewer operations. Furthermore, the orderof the operations may be changed, and/or two or more operations may becombined into a single operation. For example, the operations in methods300 (FIG. 3), 400 (FIG. 4) and/or 600 (FIG. 6) may be performed by adifferent processor in the electronic device, such as a secure enclaveprocessor.

In another exemplary embodiment, the update technique involves athree-phase process. During the first phase, an issuer security domainis selected. Then, a so-called ‘preflight script’ is sent from a serverto the electronic device. This is shown in FIG. 9, which presents adrawing illustrating a preflight script 900 in method 600 (FIG. 6). Inparticular, preflight script 900 includes one or more packages. Eachpackage includes a package AID list with one or more package AIDs thatindicate candidates for migration, a new package AID to upload to thesecure element, and a list of applet AIDs with one or more applet AIDs.The package AIDs will be updated to the new package AID and the dataassociated with the applet AIDs needs to be migrated. Preflight script900 also includes a counter value that is incremented after preflightscript 900 is played once on a given electronic device to prevent replayattacks. Moreover, preflight script 900 may be signed using anencryption key.

When preflight script 900 is executed by the operating system in thesecure element, the entry for a given applet (specified by one of theapplet AIDs) in the registry is found and transferred to a temporary ora secondary registry. Then, the applet is called using a Java CardexportData( ) and/or exportObject( ) methods (or commands). If theapplet is personalized, exportData( ) and/or exportObject( ) transferthe associated data and/or encryption keys and pins to the selectedsecurity domain. In particular, exportData( ) transfers the data andexportObject( ) transfers the encrypted keys and pins. Next, a returncommand is executed. Alternatively, if the applet is not personalized,the return command is executed without calling the applet using theexportData( ) and/or exportObject( ) methods or commands.

Furthermore, the applet is deleted. In particular, the applet is calledusing a Java Card uninstall( ) method, cleanup is performed at theApplet level, and the return command is executed. Additionally, theoperating system in the secure element deletes the applet and agarbage-collection operation is performed to reclaim the memorypreviously associated with the applet.

During the second phase, the high-end boot loader (such as updatingoperating system 234 in FIG. 2) is used to replace one or more of thespecified packages and to raise a flag, as described previously.

Furthermore, during the third phase a so-called postflight script, whichis empty except for a single application protocol data unit command suchas import, is executed by the operating system in the secure element. Inresponse, the operating system in the secure element parses thesecondary registry. For a given applet, this may involve the operatingsystem in the secure element: creating an instance of the given appletincluding a copy of the secondary registry; calling the applet using aninstall( ) method; calling the applet using an import( ) method, whichcalls an importData( ) and/or an importObject( ) methods; performingcleanup; and performing a garbage-collection operation to reclaim theassociated memory.

Note that a new version of an applet that is installed using the updatetechnique may have a new AID or, depending on the use case, mayoptionally retain the same AID as the previous version of the applet.

While the preceding embodiment used updating or migrating a personalizedapplet (i.e., one with associated data) as an illustrative example, inother embodiments the update technique may be used to update anon-personalized applet (e.g., one without associated data), such asduring manufacturing or configuring of an electronic device in afactory.

In the preceding description, we refer to ‘some embodiments.’ Note that‘some embodiments’ describes a subset of all of the possibleembodiments, but does not always specify the same subset of embodiments.

The foregoing description is intended to enable any person skilled inthe art to make and use the disclosure, and is provided in the contextof a particular application and its requirements. Moreover, theforegoing descriptions of embodiments of the present disclosure havebeen presented for purposes of illustration and description only. Theyare not intended to be exhaustive or to limit the present disclosure tothe forms disclosed. Accordingly, many modifications and variations willbe apparent to practitioners skilled in the art, and the generalprinciples defined herein may be applied to other embodiments andapplications without departing from the spirit and scope of the presentdisclosure. Additionally, the discussion of the preceding embodiments isnot intended to limit the present disclosure. Thus, the presentdisclosure is not intended to be limited to the embodiments shown, butis to be accorded the widest scope consistent with the principles andfeatures disclosed herein.

What is claimed is:
 1. An electronic device, comprising: an interfacecircuit configured to communicate with an updating device; and a secureelement comprising a previous version of an applet, a supplementalsecurity domain, and an operating system, the secure element configuredto: receive an update package from the updating device via a data storeassociated with the supplemental security domain after being providedaccess to the supplemental security domain by the operating system,wherein the update package includes an update to the previous version ofthe applet; export user data associated with the previous version of theapplet to a data store associated with the supplemental security domainafter being provided access to the supplemental security domain by theoperating system; install, by the operating system, the update to theprevious version of the applet on the secure element based at least inpart on the exporting; and in response to the update to the previousversion of the applet being installed, personalize, by the operatingsystem, the updated applet on the secure element by importing the userdata from the data store into the updated applet.
 2. The electronicdevice of claim 1, wherein the secure element is further configured to:identify, by the operating system, the previous version of the appletinstalled on the secure element by searching a registry associated withthe operating system.
 3. The electronic device of claim 1, wherein thesecure element is further configured to: verify, by the operatingsystem, the update package using an encryption key associated with thesecure element.
 4. The electronic device of claim 1, wherein the secureelement is further configured to: decrypt the update package using anencryption key associated with the secure element.
 5. The electronicdevice of claim 1, wherein the secure element is further configured to:personalize, by the operating system, the updated applet on the secureelement by importing the user data from the data store into the updatedapplet after being provided access to the supplemental security domainby the operating system.
 6. The electronic device of claim 1, whereinthe secure element is further configured to: uninstall the previousversion of the applet after the export of the user data to the datastore is complete.
 7. The electronic device of claim 1, wherein theelectronic device further comprises: a secure enclave processorconfigured to: receive the update package from the updating device; andupload the update package to the data store associated with thesupplemental security domain after being provided access to thesupplemental security domain by the operating system.
 8. Acomputer-program product for use in conjunction with a secure element inan electronic device, the computer-program product comprising anon-transitory computer-readable storage medium and a computer-programmechanism embedded therein, to update an applet installed on the secureelement in the electronic device, the computer-program mechanismincluding: instructions for receiving an update package from an updatingdevice via a data store associated with a supplemental security domainafter being provided access to the supplemental security domain by anoperating system, wherein the update package includes an update to aprevious version of the applet installed on the secure element;instructions for verifying the update package using an encryption keyassociated with the secure element; instructions for exporting user dataassociated with the previous version of the applet to the data storeassociated with the supplemental security domain after being providedaccess to the supplemental security domain by the operating system;instructions for installing the update to the previous version of theapplet on the secure element based at least in part on the exporting;and instructions for personalizing the updated applet on the secureelement by importing the user data from the data store into the updatedapplet.
 9. The computer-program product of claim 8, wherein thecomputer-program mechanism includes instructions for identifying theprevious version of the applet installed on the secure element bysearching a registry associated with the operating system.
 10. Thecomputer-program product of claim 8, wherein the computer-programmechanism includes instructions for: decrypting the update package usinga second encryption key associated with the secure element.
 11. Thecomputer-program product of claim 8, wherein the instructions forpersonalizing comprise further instructions for: personalizing theupdated applet on the secure element by importing the user data from thedata store into the updated applet after being provided access to thesupplemental security domain by the operating system.
 12. Aprocessor-implemented method for updating a payment applet installed ona secure element in an electronic device, wherein the method comprises:receiving an update package from an updating device via a data storeassociated with a supplemental security domain after being providedaccess to the supplemental security domain by an operating system,wherein the update package includes the update to a previous version ofthe payment applet; exporting user data associated with the previousversion of the payment applet to the data store associated with thesupplemental security domain after being provided access to thesupplemental security domain by the operating system, wherein the userdata comprises at least one of a financial credential, a personalidentifier number associated with the payment applet, and an encryptionkey associated with the payment applet; installing the update to thepayment applet on the secure element based at least in part on theexporting; in response to the update to the payment applet beinginstalled, personalizing the updated payment applet on the secureelement by importing the user data from the data store into the updatedpayment applet; and conducting a financial transaction using the updatedpayment applet, wherein the financial transaction is conducted using theuser data imported from the data store into the updated payment applet.13. The method of claim 12, further comprising: identifying the previousversion of the payment applet installed on the secure element bysearching a registry associated with the operating system.
 14. Themethod of claim 12, further comprising: verifying the update packageusing an encryption key associated with the secure element.
 15. Themethod of claim 12, further comprising: decrypting the update packageusing an encryption key associated with the secure element.
 16. Themethod of claim 12, wherein the personalizing further comprisespersonalizing the updated payment applet on the secure element byimporting the user data from the data store into the updated paymentapplet after being provided access to the supplemental security domainby the operating system.
 17. The method of claim 12, wherein theconducting further comprises conducting the financial transaction usingthe updated payment applet in response to receiving a payment commandfrom a secure enclave processor or in response to the electronic devicebeing in a proximity to a second electronic device.